language en

Linked.Archi UML 2.5.1 Ontology

Release: 2025-12-01

Modified on: 2026-02-01
This version:
https://meta.linked.archi/uml/onto/0.1.0#
Revision:
0.1.0
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
Source:
https://www.omg.org/spec/MOF/2.5.1/
https://www.omg.org/spec/ODM/1.1/
https://www.omg.org/spec/UML/2.5.1/
See also:
https://www.iso.org/standard/32624.html
https://www.iso.org/standard/52854.html
https://www.omg.org/spec/MOF/2.5.1/
https://www.omg.org/spec/ODM/1.1/
https://www.omg.org/spec/UML/2.5.1/
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Kalin Maldzhanski. Linked.Archi UML 2.5.1 Ontology. Revision: 0.1.0. Retrieved from: https://meta.linked.archi/uml/onto/0.1.0#
Provenance of this page
draft

Linked.Archi UML 2.5.1 Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Annotation Properties

Linked.Archi UML 2.5.1 Ontology: Description back to ToC

RDF/OWL formalization of the OMG Unified Modeling Language (UML) 2.5.1 metamodel for use in the Linked.Archi architecture knowledge graph. Covers structural classifiers (Class, Interface, Component, Package), behavioral elements (Activity, StateMachine, Interaction), deployment concepts (Node, Artifact), and use cases (Actor, UseCase). Relationship types follow the Linked.Archi three-declaration qualified relationship pattern. This ontology is INFORMED BY the OMG Ontology Definition Metamodel (ODM, formal/2014-09-02) but does NOT apply ODM directly. ODM Annex D maps UML model instances (M1) to OWL; this ontology represents the UML metamodel itself (M2) as OWL classes so that UML model data can be typed in a knowledge graph. We adopt ODM principles (Class→owl:Class, Generalization→rdfs:subClassOf, Package→owl:Ontology) but depart from ODM for associations (three-declaration pattern), enumerations (SKOS), constraints (SHACL), and domain/range (arch:domainIncludes). See the skos:scopeNote for the full comparison. This is not an official OMG document. It is a Linked.Archi interpretation of the UML specification for semantic architecture modeling.

Cross-reference for Linked.Archi UML 2.5.1 Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi UML 2.5.1 Ontology.

Classes

Abstractionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Abstraction

A qualified relationship representing a UML Abstraction — a Dependency relating elements at different abstraction levels.
has super-classes
Dependency c
is in range of
qualified abstracts op

Accept Event Actionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#AcceptEventAction

An AcceptEventAction waits for the occurrence of one or more specific events. Maps to UML 2.5.1 §16.10 AcceptEventAction.
has super-classes
Action c

Actionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Action

An Action is the fundamental unit of executable functionality. The execution of an Action represents some transformation or processing in the modeled system. Maps to UML 2.5.1 §16.2 Action.
has super-classes
Activity Node c
has sub-classes
Accept Event Action c, Call Action c, Send Signal Action c

Activityc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Activity

An Activity specifies the coordination of executions of subordinate Behaviors, using a control and data flow model. Maps to UML 2.5.1 §15.2 Activity.
has super-classes
Behavior c

Activity Edgec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ActivityEdge

An ActivityEdge is an abstract class for directed connections between two ActivityNodes. Maps to UML 2.5.1 §15.2 ActivityEdge.
has super-classes
Redefinable Element c, qualified relationship c
has sub-classes
Control Flow c, Object Flow c

Activity Final Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ActivityFinalNode

An ActivityFinalNode is a FinalNode that stops all flows in an Activity. Maps to UML 2.5.1 §15.3 ActivityFinalNode.
has super-classes
Final Node c

Activity Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ActivityNode

An ActivityNode is an abstract class for points in the flow of an Activity connected by ActivityEdges. Maps to UML 2.5.1 §15.2 ActivityNode.
has super-classes
Redefinable Element c
has sub-classes
Action c, Control Node c, Object Node c

Activity Partitionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ActivityPartition

An ActivityPartition is a kind of ActivityGroup for identifying ActivityNodes that have some characteristic in common (swim lanes). Maps to UML 2.5.1 §15.6 ActivityPartition.
has super-classes
Named Element c

Actorc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Actor

An Actor specifies a role played by a user or any other system that interacts with the subject. Actors model a type of role played by an entity that interacts with the subject but which is external to it.
has super-classes
Behaviored Classifier c

Aggregationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Aggregation

A qualified relationship representing a UML shared aggregation — a whole-part relationship where the part can exist independently.
has super-classes
Association c
is in range of
qualified aggregates op

Artifactc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Artifact

An Artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system. Examples of Artifacts include model files, source files, scripts, and binary executable files.
has super-classes
Classifier c, Deployment Target c
has sub-classes
Deployment Specification c

Associationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Association

A qualified relationship representing a UML Association — a structural relationship between Classifiers that specifies connections among their instances. Maps to UML 2.5.1 §11.5 Association.
has super-classes
qualified relationship c
has sub-classes
Aggregation c, Composition c
is in range of
qualified associated with op

Behaviorc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Behavior

A Behavior is a specification of how its context BehavioredClassifier changes state over time. It is the abstract base for Activity, StateMachine, Interaction, and OpaqueBehavior. Maps to UML 2.5.1 §13.2 Behavior.
has super-classes
Class c
has sub-classes
Activity c, Interaction c, Opaque Behavior c, State Machine c

Behavior Execution Specificationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#BehaviorExecutionSpecification

A BehaviorExecutionSpecification is an ExecutionSpecification that represents the execution of a Behavior (as opposed to an opaque action). It references the Behavior being executed. Maps to UML 2.5.1 §17.5 BehaviorExecutionSpecification. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="BehaviorExecutionSpecification").
has super-classes
Execution Specification c

Behaviored Classifierc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#BehavioredClassifier

A Classifier that may have InterfaceRealizations and owned Behaviors. Maps to UML 2.5.1 §10.5 BehavioredClassifier.
has super-classes
Classifier c
has sub-classes
Actor c, Class c, Collaboration c, Use Case c

Call Actionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#CallAction

A CallAction is an Action that invokes a Behavior or Operation. Maps to UML 2.5.1 §16.3 CallAction.
has super-classes
Action c

Classc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Class

A Class is a kind of EncapsulatedClassifier whose Features are Properties, Operations, Receptions, Ports, and Connectors. A Class may have attributes (Properties owned by the Class), some of which may represent the ends of binary Associations.
has super-classes
Behaviored Classifier c, Encapsulated Classifier c
has sub-classes
Behavior c, Component c, Node c, Stereotype c

Classifierc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Classifier

A Classifier represents a classification of instances according to their features. It is the abstract base for Class, Interface, DataType, Component, and other concrete classifiers. Maps to UML 2.5.1 §9.2 Classifier. ODM maps MOF::Class to owl:Class; Classifier is the UML-level abstraction.
has super-classes
Namespace c, Redefinable Element c, Type c
has sub-classes
Artifact c, Behaviored Classifier c, Data Type c, Information Item c, Interface c, Signal c, Structured Classifier c

Collaborationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Collaboration

A Collaboration defines a set of cooperating roles and their connectors. It represents a pattern of interaction. Maps to UML 2.5.1 §11.7 Collaboration.
has super-classes
Behaviored Classifier c, Structured Classifier c

Collaboration Usec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#CollaborationUse

A CollaborationUse represents the application of a pattern described by a Collaboration to a specific situation. Maps to UML 2.5.1 §11.7 CollaborationUse.
has super-classes
Named Element c

Combined Fragmentc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#CombinedFragment

A CombinedFragment defines an expression of InteractionFragments governed by an interaction operator. The operator (alt, opt, loop, break, par, seq, strict, critical, neg, assert, ignore, consider) determines the semantics of how the contained InteractionOperands are combined. A CombinedFragment is the mechanism for expressing control flow (conditionals, loops, parallelism) within a sequence diagram. Maps to UML 2.5.1 §17.6 CombinedFragment. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="CombinedFragment").
Example
An "alt" fragment for login success/failure:
  ex:alt-login a uml:CombinedFragment ;
      uml:interactionOperator <https://meta.linked.archi/uml/reference-data#Alt> ;
      uml:hasOperand ex:operand-success, ex:operand-failure ;
      uml:sequenceNumber 5 .
has super-classes
Interaction Fragment c

Commentc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Comment

A textual annotation attached to a set of elements. Maps to UML 2.5.1 §7.2 Comment.
has super-classes
Element c

Communication Pathc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#CommunicationPath

A CommunicationPath is an association between two DeploymentTargets, through which they are able to exchange signals and messages. Maps to UML 2.5.1 §19.4 CommunicationPath.
has super-classes
Element c

Componentc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Component

A Component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment. A Component specifies a formal contract of the services that it provides to its clients and those that it requires from other Components or services in the system in terms of its provided and required Interfaces.
has super-classes
Class c

Compositionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Composition

A qualified relationship representing a UML composite aggregation — a strong whole-part relationship where the part cannot exist without the whole.
has super-classes
Association c
is in range of
qualified composed of op

Connectorc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Connector

A Connector specifies links that enable communication between two or more instances. Each Connector may be attached to two or more ConnectableElements (Ports, Properties). Maps to UML 2.5.1 §11.2 Connector.
has super-classes
Feature c

Connector Endc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ConnectorEnd

A ConnectorEnd is an endpoint of a Connector, which attaches the Connector to a ConnectableElement. Maps to UML 2.5.1 §11.2 ConnectorEnd.
has super-classes
Element c

Constraintc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Constraint

A condition or restriction expressed in natural language or in a machine-readable language for the purpose of declaring some of the semantics of an element. Maps to UML 2.5.1 §7.6 Constraint.
has super-classes
Packageable Element c
has sub-classes
Interaction Constraint c

Continuationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Continuation

A Continuation is an InteractionFragment that defines a continuation label within a CombinedFragment with operator "alt". Continuations always occur as the very first or very last InteractionFragment of the enclosing InteractionOperand, and are global (cover all Lifelines covered by the enclosing operator). Maps to UML 2.5.1 §17.6 Continuation. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Continuation").
has super-classes
Interaction Fragment c

Control Flowc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ControlFlow

A ControlFlow is an ActivityEdge traversed by control tokens only. Maps to UML 2.5.1 §15.2 ControlFlow.
has super-classes
Activity Edge c

Control Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ControlNode

A ControlNode is an abstract ActivityNode used to coordinate the flows between other nodes. Maps to UML 2.5.1 §15.3 ControlNode.
has super-classes
Activity Node c
has sub-classes
Decision Node c, Final Node c, Fork Node c, Initial Node c, Join Node c, Merge Node c

Data Typec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#DataType

A DataType is a type whose instances are identified only by their value. Maps to UML 2.5.1 §10.2 DataType. ODM Annex D.2.4 (Table D.10) maps to rdfs:Datatype or owl:Class depending on whether it has structural features.
has super-classes
Classifier c
has sub-classes
Enumeration c, Primitive Type c

Decision Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#DecisionNode

A DecisionNode is a ControlNode that chooses between outgoing flows. Maps to UML 2.5.1 §15.3 DecisionNode.
has super-classes
Control Node c

Dependencyc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Dependency

A qualified relationship representing a UML Dependency — a supplier/client relationship where changes to the supplier may affect the client.
has super-classes
qualified relationship c
has sub-classes
Abstraction c, Usage c
is in range of
qualified depends on op

Deploymentc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Deployment

A qualified relationship representing a UML Deployment — an Artifact is deployed on a DeploymentTarget (Node, Device, ExecutionEnvironment).
has super-classes
qualified relationship c
is in range of
qualified deployed on op

Deployment Specificationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#DeploymentSpecification

A DeploymentSpecification specifies a set of properties that determine execution parameters of a component artifact deployed on a node. Maps to UML 2.5.1 §19.3 DeploymentSpecification.
has super-classes
Artifact c

Deployment Targetc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#DeploymentTarget

A DeploymentTarget is the general concept of a location in which a DeployedArtifact can be deployed. Maps to UML 2.5.1 §19.2 DeploymentTarget.
has super-classes
Named Element c
has sub-classes
Artifact c, Node c

Destruction Occurrence Specificationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#DestructionOccurrenceSpecification

A DestructionOccurrenceSpecification models the destruction of an object. It is shown as an X at the bottom of a Lifeline. No other OccurrenceSpecifications on the same Lifeline may appear below a DestructionOccurrenceSpecification within the same InteractionOperand. Maps to UML 2.5.1 §17.4 DestructionOccurrenceSpecification. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="DestructionOccurrenceSpecification").
has super-classes
Message Occurrence Specification c

Devicec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Device

A Device is a physical computational resource with processing capability upon which artifacts may be deployed. Maps to UML 2.5.1 §19.4 Device.
has super-classes
Node c

Elementc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Element

The root metaclass for all UML model elements. Maps to UML 2.5.1 §7.2 Element. In the ODM mapping, this corresponds to the root MOF::Element mapped to owl:Class.
has super-classes
element c
has sub-classes
Comment c, Communication Path c, Connector End c, Information Flow c, Manifestation c, Named Element c, Profile Application c

Encapsulated Classifierc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#EncapsulatedClassifier

A StructuredClassifier that may have Ports. Maps to UML 2.5.1 §11.2 EncapsulatedClassifier.
has super-classes
Structured Classifier c
has sub-classes
Class c

Enumerationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Enumeration

An Enumeration is a DataType whose values are enumerated in the model as EnumerationLiterals. Maps to UML 2.5.1 §10.2 Enumeration. In Linked.Archi, enumeration values are modeled as SKOS concepts in the reference data (see DD-5).
has super-classes
Data Type c

Enumeration Literalc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#EnumerationLiteral

A user-defined data value for an Enumeration. Maps to UML 2.5.1 §10.2 EnumerationLiteral.
has super-classes
Named Element c

Eventc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Event

An Event is the specification of some occurrence that may potentially trigger effects by an object. Maps to UML 2.5.1 §13.3 Event.
has super-classes
Packageable Element c

Execution Environmentc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ExecutionEnvironment

An ExecutionEnvironment is a Node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts. Maps to UML 2.5.1 §19.4 ExecutionEnvironment.
has super-classes
Node c

Execution Occurrence Specificationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ExecutionOccurrenceSpecification

An ExecutionOccurrenceSpecification represents moments in time at which Actions or Behaviors start or finish. It is the concrete OccurrenceSpecification subclass used as the start and finish points of an ExecutionSpecification (activation bar). Unlike MessageOccurrenceSpecification (which represents message send/receive), ExecutionOccurrenceSpecification represents the beginning or end of an execution period on a Lifeline. Maps to UML 2.5.1 §17.5 ExecutionOccurrenceSpecification. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="ExecutionOccurrenceSpecification").
has super-classes
Occurrence Specification c

Execution Specificationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ExecutionSpecification

An ExecutionSpecification is a specification of the execution of a unit of Behavior or Action within a Lifeline. It is depicted as the activation bar (thin rectangle) on a Lifeline in a sequence diagram. An ExecutionSpecification has a start OccurrenceSpecification and a finish OccurrenceSpecification that delimit the period during which the Lifeline is actively executing. Maps to UML 2.5.1 §17.5 ExecutionSpecification. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="ExecutionSpecification").
has super-classes
Interaction Fragment c
has sub-classes
Behavior Execution Specification c

Extendc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Extend

A qualified relationship representing a UML Extend — an extending UseCase conditionally augments the behavior of an extended UseCase.
has super-classes
qualified relationship c
is in range of
qualified extends op

Extension Pointc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ExtensionPoint

An ExtensionPoint identifies a point in the behavior of a UseCase where that behavior can be extended by the behavior of some other UseCase. Maps to UML 2.5.1 §18.2 ExtensionPoint.
has super-classes
Redefinable Element c

Featurec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Feature

A Feature declares a behavioral or structural characteristic of Classifiers. Maps to UML 2.5.1 §9.4 Feature.
has super-classes
Redefinable Element c
has sub-classes
Connector c, Operation c, Structural Feature c

Final Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#FinalNode

A FinalNode is an abstract ControlNode at which a flow in an Activity stops. Maps to UML 2.5.1 §15.3 FinalNode.
has super-classes
Control Node c
has sub-classes
Activity Final Node c, Flow Final Node c

Final Statec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#FinalState

A FinalState represents the completion of activity in the enclosing Region. Maps to UML 2.5.1 §14.2 FinalState.
has super-classes
State c

Flow Final Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#FlowFinalNode

A FlowFinalNode is a FinalNode that terminates a flow without terminating the overall Activity. Maps to UML 2.5.1 §15.3 FlowFinalNode.
has super-classes
Final Node c

Fork Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ForkNode

A ForkNode is a ControlNode that splits a flow into multiple concurrent flows. Maps to UML 2.5.1 §15.3 ForkNode.
has super-classes
Control Node c

Function Behaviorc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#FunctionBehavior

A FunctionBehavior is an OpaqueBehavior that does not access or modify any objects or other external data. Maps to UML 2.5.1 §13.2 FunctionBehavior.
has super-classes
Opaque Behavior c

Gatec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Gate

A Gate is a MessageEnd that serves as a connection point for relating a Message outside an InteractionFragment with a Message inside the InteractionFragment. Gates are used at the boundary of Interactions (formalGate) and CombinedFragments (cfragmentGate) to allow Messages to cross those boundaries, and at InteractionUse boundaries (actualGate) to bind to the referenced Interaction's formalGates. Maps to UML 2.5.1 §17.4 Gate. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Gate").
has super-classes
Message End c

General Orderingc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#GeneralOrdering

A GeneralOrdering represents a binary relation between two OccurrenceSpecifications, to describe that one OccurrenceSpecification must occur before the other in a valid trace. This mechanism provides the ability to define partial orders of OccurrenceSpecifications that may otherwise not have a specified order — for example, events on different Lifelines that are not connected by a Message but must still be ordered. Maps to UML 2.5.1 §17.3 GeneralOrdering. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="GeneralOrdering").
editorial note
In UML XMI, GeneralOrdering has two properties: - before : OccurrenceSpecification [1] — the occurrence that must happen first - after : OccurrenceSpecification [1] — the occurrence that must happen second In Linked.Archi RDF, these are modeled as :orderingBefore and :orderingAfter object properties on the GeneralOrdering instance. See .reference/omg/uml/ptc-18-01-01.xmi lines 9928–9963.
has super-classes
Named Element c

Generalizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Generalization

A qualified relationship representing a UML Generalization — a taxonomic relationship from specific to general Classifier.
has super-classes
qualified relationship c
is in range of
qualified generalizes op

Includec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Include

A qualified relationship representing a UML Include — a base UseCase incorporates the behavior of an included UseCase.
has super-classes
qualified relationship c
is in range of
qualified includes op

Information Flowc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InformationFlow

An InformationFlow specifies that one or more information items circulate from its sources to its targets. Maps to UML 2.5.1 §20.2 InformationFlow.
has super-classes
Element c, qualified relationship c

Information Itemc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InformationItem

An InformationItem represents an abstraction of data that can be conveyed between two entities. Maps to UML 2.5.1 §20.2 InformationItem.
has super-classes
Classifier c

Initial Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InitialNode

An InitialNode is a ControlNode at which flow starts when the Activity is invoked. Maps to UML 2.5.1 §15.3 InitialNode.
has super-classes
Control Node c

Interactionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Interaction

An Interaction is a unit of Behavior that focuses on the observable exchange of information between connectable elements. It owns an ordered set of InteractionFragments (the fragment property), a set of Lifelines (the participants), and a set of Messages (the communications). An Interaction is itself an InteractionFragment, allowing nesting. Maps to UML 2.5.1 §17.2 Interaction. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Interaction").
Example
A "Login" sequence diagram is modeled as:
  ex:LoginInteraction a uml:Interaction ;
      skos:prefLabel "Login"@en ;
      uml:hasLifeline ex:ll-user, ex:ll-auth, ex:ll-db ;
      uml:hasMessage ex:msg-authenticate, ex:msg-validate, ex:msg-result, ex:msg-token ;
      uml:hasFragment ex:mos1-send, ex:mos1-recv, ex:mos2-send, ex:mos2-recv .
has super-classes
Behavior c, Interaction Fragment c

Interaction Constraintc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InteractionConstraint

An InteractionConstraint is a Boolean expression that guards an operand in a CombinedFragment. It determines whether the InteractionOperand is executed. For loop CombinedFragments, it may also specify minint and maxint bounds. Maps to UML 2.5.1 §17.6 InteractionConstraint. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionConstraint").
has super-classes
Constraint c

Interaction Fragmentc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InteractionFragment

InteractionFragment is the abstract base metaclass for all elements that can appear in the ordered fragment list of an Interaction or InteractionOperand. Every InteractionFragment is conceptually like an Interaction by itself — it covers one or more Lifelines and occupies a position in the temporal ordering of the enclosing Interaction. Concrete subclasses include OccurrenceSpecification, CombinedFragment, InteractionUse, ExecutionSpecification, and StateInvariant. Maps to UML 2.5.1 §17.3 InteractionFragment. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionFragment").
editorial note
Key properties from the UML metamodel: - covered : Lifeline [0..*] — the lifelines this fragment involves - enclosingInteraction : Interaction [0..1] — the owning Interaction - enclosingOperand : InteractionOperand [0..1] — the owning operand (if nested) - generalOrdering : GeneralOrdering [0..*] {composite} — explicit ordering constraints See .reference/omg/uml/ptc-18-01-01.xmi lines 10157–10215.
has super-classes
Named Element c
has sub-classes
Combined Fragment c, Continuation c, Execution Specification c, Interaction c, Interaction Operand c, Interaction Use c, Occurrence Specification c, State Invariant c

Interaction Operandc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InteractionOperand

An InteractionOperand is contained in a CombinedFragment and represents one operand of the expression given by the enclosing CombinedFragment. It owns an ordered set of InteractionFragments (its own fragment list) and may have a guard (InteractionConstraint) that determines whether the operand is executed. Maps to UML 2.5.1 §17.6 InteractionOperand. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionOperand").
has super-classes
Interaction Fragment c, Namespace c

Interaction Usec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InteractionUse

An InteractionUse refers to another Interaction. It is a means of copying a portion of the referred Interaction into the enclosing Interaction — the "ref" fragment in sequence diagram notation. InteractionUse enables modular composition of interactions by referencing reusable sub-sequences. Maps to UML 2.5.1 §17.7 InteractionUse. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionUse").
has super-classes
Interaction Fragment c

Interfacec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Interface

An Interface is a kind of Classifier that represents a declaration of a set of public Features and obligations that together constitute a coherent service. An Interface specifies a contract; any instance of a Classifier that realizes the Interface shall fulfill that contract.
has super-classes
Classifier c

Interface Realizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#InterfaceRealization

A qualified relationship representing a UML InterfaceRealization — a BehavioredClassifier fulfills the contract of an Interface.
has super-classes
Realization c
is in range of
qualified realizes interface op

Join Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#JoinNode

A JoinNode is a ControlNode that synchronizes multiple flows. Maps to UML 2.5.1 §15.3 JoinNode.
has super-classes
Control Node c

Lifelinec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Lifeline

A Lifeline represents an individual participant in the Interaction. While parts and structural features may have multiplicity greater than 1, Lifelines represent only one interacting entity. A Lifeline is depicted as a vertical dashed line with a header box showing the participant name and type. It references a ConnectableElement (Property, Port, Parameter) within the classifier that contains the enclosing Interaction. Maps to UML 2.5.1 §17.3 Lifeline. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Lifeline").
has super-classes
Named Element c

Manifestationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Manifestation

A Manifestation is the concrete physical rendering of one or more model elements by an artifact. Maps to UML 2.5.1 §19.3 Manifestation.
has super-classes
Element c

Merge Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#MergeNode

A MergeNode is a ControlNode that brings together multiple alternate flows without synchronization. Maps to UML 2.5.1 §15.3 MergeNode.
has super-classes
Control Node c

Messagec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Message

A Message defines a particular communication between Lifelines of an Interaction. Each Message has a sendEvent and a receiveEvent (both MessageEnd instances), a messageSort indicating the type of communication (synchCall, asynchCall, asynchSignal, createMessage, deleteMessage, reply), and an optional signature referencing the Operation or Signal being invoked. Messages are the arrows in a sequence diagram. Maps to UML 2.5.1 §17.4 Message. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Message").
editorial note
Message ordering in a sequence diagram is NOT a property of the Message itself — it is determined by the position (sequenceNumber) of the MessageOccurrenceSpecifications that serve as its sendEvent and receiveEvent within the Interaction::fragment ordered collection. Message M1 precedes M2 if M1.sendEvent.sequenceNumber < M2.sendEvent.sequenceNumber. See UML-DD-9 in design-decisions.md for the full rationale.
has super-classes
Named Element c

Message Endc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#MessageEnd

MessageEnd is an abstract specialization of NamedElement that represents what can occur at the end of a Message. A MessageEnd is either a MessageOccurrenceSpecification (on a Lifeline) or a Gate (at an Interaction or CombinedFragment boundary). The sendEvent and receiveEvent properties of Message point to MessageEnd instances. Maps to UML 2.5.1 §17.4 MessageEnd. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="MessageEnd").
has super-classes
Named Element c
has sub-classes
Gate c, Message Occurrence Specification c

Message Occurrence Specificationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#MessageOccurrenceSpecification

A MessageOccurrenceSpecification represents the sending or receiving of a Message on a specific Lifeline. It is both an OccurrenceSpecification (a point in time on a Lifeline) and a MessageEnd (an endpoint of a Message). This dual inheritance is the key structural element that connects Messages to the temporal ordering: the sequenceNumber of the MessageOccurrenceSpecification determines when the send or receive occurs relative to other events on the same Lifeline. Maps to UML 2.5.1 §17.4 MessageOccurrenceSpecification. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="MessageOccurrenceSpecification").
Example
For a synchronous call "authenticate" from User to AuthService:
  ex:mos1-send a uml:MessageOccurrenceSpecification ;
      uml:covered ex:ll-user ;
      uml:sequenceNumber 1 .
  ex:mos1-recv a uml:MessageOccurrenceSpecification ;
      uml:covered ex:ll-auth ;
      uml:sequenceNumber 2 .
  ex:msg-authenticate uml:sendEvent ex:mos1-send ;
      uml:receiveEvent ex:mos1-recv .
has super-classes
Message End c, Occurrence Specification c
has sub-classes
Destruction Occurrence Specification c

Modelc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Model

A Model is a Package that contains a complete description of the modeled system from a particular viewpoint. Maps to UML 2.5.1 §12.2 Model.
has super-classes
Package c

Named Elementc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#NamedElement

An element that has a name and visibility within a namespace. Maps to UML 2.5.1 §7.4 NamedElement.
has super-classes
Element c
has sub-classes
Activity Partition c, Collaboration Use c, Deployment Target c, Enumeration Literal c, General Ordering c, Interaction Fragment c, Lifeline c, Message c, Message End c, Namespace c, Packageable Element c, Redefinable Element c, Trigger c, Typed Element c, Vertex c

Namespacec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Namespace

A named element that can own other named elements, providing a naming scope. Maps to UML 2.5.1 §7.4 Namespace.
has super-classes
Named Element c
has sub-classes
Classifier c, Interaction Operand c, Operation c, Package c, Region c, State c, Transition c

Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Node

A Node is a computational resource upon which Artifacts may be deployed, via Deployment relationships, for execution. Nodes can be interconnected through communication paths.
has super-classes
Class c, Deployment Target c
has sub-classes
Device c, Execution Environment c

Object Flowc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ObjectFlow

An ObjectFlow is an ActivityEdge that can have objects or data passing along it. Maps to UML 2.5.1 §15.2 ObjectFlow.
has super-classes
Activity Edge c

Object Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ObjectNode

An ObjectNode is an ActivityNode that indicates an instance of a particular Classifier, possibly in a particular state, may be available at a particular point in the Activity. Maps to UML 2.5.1 §15.4 ObjectNode.
has super-classes
Activity Node c, Typed Element c

Occurrence Specificationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#OccurrenceSpecification

An OccurrenceSpecification is the basic semantic unit of Interactions. The sequences of occurrences specified by them are the meanings of Interactions. Each OccurrenceSpecification covers exactly one Lifeline and represents a single point in time on that Lifeline — typically the sending or receiving of a Message, or the start/finish of an ExecutionSpecification. Maps to UML 2.5.1 §17.4 OccurrenceSpecification. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="OccurrenceSpecification").
editorial note
Key properties: - covered : Lifeline [1] — redefines InteractionFragment::covered to exactly one - toAfter : GeneralOrdering [0..*] — orderings where this is the "before" element - toBefore : GeneralOrdering [0..*] — orderings where this is the "after" element See .reference/omg/uml/ptc-18-01-01.xmi lines 10986–11035.
has super-classes
Interaction Fragment c
has sub-classes
Execution Occurrence Specification c, Message Occurrence Specification c

Opaque Behaviorc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#OpaqueBehavior

An OpaqueBehavior is a Behavior whose specification is given in a textual language other than UML. Maps to UML 2.5.1 §13.2 OpaqueBehavior.
has super-classes
Behavior c
has sub-classes
Function Behavior c

Operationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Operation

A behavioral feature of a Classifier that specifies the name, type, parameters, and constraints for invoking an associated Behavior. Maps to UML 2.5.1 §9.6 Operation.
has super-classes
Feature c, Namespace c

Packagec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Package

A Package is used to group elements and provides a namespace for the grouped elements. Maps to UML 2.5.1 §12.2 Package. ODM Annex D.3.2 maps MOF::Package to owl:Ontology.
has super-classes
Namespace c, Packageable Element c
has sub-classes
Model c, Profile c

Package Importc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#PackageImport

A qualified relationship representing a UML PackageImport.
has super-classes
qualified relationship c
is in range of
qualified imports package op

Package Mergec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#PackageMerge

A qualified relationship representing a UML PackageMerge.
has super-classes
qualified relationship c
is in range of
qualified merges package op

Packageable Elementc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#PackageableElement

A named element that may be owned directly by a Package. Maps to UML 2.5.1 §7.4 PackageableElement.
has super-classes
Named Element c
has sub-classes
Constraint c, Event c, Package c, Type c

Parameterc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Parameter

A specification of an argument used to pass information into or out of an invocation of a BehavioralFeature. Maps to UML 2.5.1 §9.4 Parameter.
has super-classes
Typed Element c

Portc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Port

A Port is a property of an EncapsulatedClassifier that specifies a distinct interaction point between the classifier and its environment or between the classifier and its internal parts. Maps to UML 2.5.1 §11.3 Port.
has super-classes
Property c

Primitive Typec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#PrimitiveType

A PrimitiveType defines a predefined DataType without any substructure. Typical examples are Integer, Boolean, String, and UnlimitedNatural. Maps to UML 2.5.1 §10.2 PrimitiveType.
has super-classes
Data Type c

Profilec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Profile

A Profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain. Maps to UML 2.5.1 §12.3 Profile.
has super-classes
Package c

Profile Applicationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#ProfileApplication

A ProfileApplication is used to show which Profiles have been applied to a Package. Maps to UML 2.5.1 §12.3 ProfileApplication.
has super-classes
Element c

Propertyc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Property

A Property is a StructuralFeature that represents an attribute of a Classifier or an end of an Association. Maps to UML 2.5.1 §9.5 Property. ODM Annex D.3.4 maps UML Property to owl:DatatypeProperty (for attributes) or owl:ObjectProperty (for association ends).
has super-classes
Structural Feature c
has sub-classes
Port c

Pseudostatec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Pseudostate

A Pseudostate is an abstraction that encompasses different types of transient Vertices in the StateMachine graph (initial, choice, junction, fork, join, etc.). Maps to UML 2.5.1 §14.3 Pseudostate.
has super-classes
Vertex c

Realizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Realization

A qualified relationship representing a UML Realization — a relationship between a specification and its implementation.
has super-classes
qualified relationship c
has sub-classes
Interface Realization c
is in range of
qualified realizes op

Redefinable Elementc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#RedefinableElement

An element that, when defined in the context of a classifier, can be redefined more specifically in the context of another classifier that specializes the first. Maps to UML 2.5.1 §7.6 RedefinableElement.
has super-classes
Named Element c
has sub-classes
Activity Edge c, Activity Node c, Classifier c, Extension Point c, Feature c

Regionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Region

A Region is a top-level part of a StateMachine or a composite State, containing States and Transitions. Maps to UML 2.5.1 §14.2 Region.
has super-classes
Namespace c

Send Signal Actionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#SendSignalAction

A SendSignalAction creates a Signal instance and transmits it to the target object. Maps to UML 2.5.1 §16.3 SendSignalAction.
has super-classes
Action c

Signalc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Signal

A Signal is a specification of a kind of communication between objects in which a reaction is asynchronously triggered in the receiver without a reply. Maps to UML 2.5.1 §10.3 Signal.
has super-classes
Classifier c

Statec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#State

A State models a situation during which some invariant condition holds. The invariant may represent a static situation such as an object waiting for some external event. Maps to UML 2.5.1 §14.2 State.
has super-classes
Namespace c, Vertex c
has sub-classes
Final State c

State Invariantc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#StateInvariant

A StateInvariant is a runtime constraint on the participants of the Interaction. It specifies a condition that must hold at the point in time where the StateInvariant appears on a Lifeline. It covers exactly one Lifeline. Maps to UML 2.5.1 §17.8 StateInvariant. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="StateInvariant").
has super-classes
Interaction Fragment c

State Machinec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#StateMachine

A StateMachine specifies the behavior of a part of a system through a finite state-transition system. Maps to UML 2.5.1 §14.2 StateMachine.
has super-classes
Behavior c

Stereotypec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Stereotype

A Stereotype defines how an existing metaclass may be extended as part of a Profile. Maps to UML 2.5.1 §12.3 Stereotype. In the ODM mapping, stereotypes become OWL classes that extend the stereotyped metaclass via rdfs:subClassOf.
has super-classes
Class c

Structural Featurec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#StructuralFeature

A typed feature of a Classifier that specifies the structure of instances. Maps to UML 2.5.1 §9.4 StructuralFeature.
has super-classes
Feature c, Typed Element c
has sub-classes
Property c

Structured Classifierc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#StructuredClassifier

A Classifier whose behavior can be fully or partly described by the collaboration of owned or referenced instances. Maps to UML 2.5.1 §11.2 StructuredClassifier.
has super-classes
Classifier c
has sub-classes
Collaboration c, Encapsulated Classifier c

Transitionc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Transition

A Transition is a directed relationship between a source Vertex and a target Vertex. It may be part of a compound transition, which takes the StateMachine from one stable State configuration to another. Maps to UML 2.5.1 §14.2 Transition.
has super-classes
Namespace c, qualified relationship c

Triggerc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Trigger

A Trigger specifies an Event that may cause the execution of an associated Behavior. Maps to UML 2.5.1 §13.3 Trigger.
has super-classes
Named Element c

Typec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Type

A Type constrains the values represented by a TypedElement. Maps to UML 2.5.1 §7.5 Type.
has super-classes
Packageable Element c
has sub-classes
Classifier c

Typed Elementc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#TypedElement

A named element that has a type. Maps to UML 2.5.1 §7.5 TypedElement.
has super-classes
Named Element c
has sub-classes
Object Node c, Parameter c, Structural Feature c

Usagec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Usage

A qualified relationship representing a UML Usage — a Dependency where the client requires the supplier for its implementation.
has super-classes
Dependency c
is in range of
qualified uses op

Use Casec back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#UseCase

A UseCase specifies a set of actions performed by its subjects, which yields an observable result that is of value for one or more Actors or other stakeholders of the subject.
has super-classes
Behaviored Classifier c

Vertexc back to ToC or Class ToC

IRI: https://meta.linked.archi/uml/onto#Vertex

A Vertex is an abstraction of a node in a StateMachine graph. It can be the source or target of any number of Transitions. Maps to UML 2.5.1 §14.2 Vertex.
has super-classes
Named Element c
has sub-classes
Pseudostate c, State c

Object Properties

Abstractsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#abstracts

A Dependency relating two elements at different abstraction levels. Maps to UML 2.5.1 §7.7 Abstraction.

Actual Gateop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#actualGate

The Gates on an InteractionUse that bind to the formalGates of the referenced Interaction. Actual gates connect messages in the enclosing Interaction to the formal interface of the referenced Interaction. Maps to UML 2.5.1 §17.7 InteractionUse::actualGate [0..*] {composite}. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionUse-actualGate").

Aggregatesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#aggregates

A whole-part relationship where the part can exist independently of the whole (shared aggregation). Maps to UML 2.5.1 §11.5 Property::aggregation = shared.

Associated Withop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#associatedWith

A semantic connection between Classifiers. Maps to UML 2.5.1 §11.5 Association. ODM Annex D.3.5 maps UML binary Association to owl:ObjectProperty.

CFragment Gateop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#cfragmentGate

The Gates owned by a CombinedFragment, through which messages can cross the CombinedFragment boundary. These gates connect messages outside the fragment to messages inside its operands. Maps to UML 2.5.1 §17.6 CombinedFragment::cfragmentGate [0..*] {composite}. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="CombinedFragment-cfragmentGate").

Composed Ofop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#composedOf

A strong whole-part relationship where the part cannot exist without the whole (composite aggregation). Deletion of the whole cascades to the parts. Maps to UML 2.5.1 §11.5 Property::aggregation = composite.

Coveredop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#covered

References the Lifeline(s) that an InteractionFragment involves. For OccurrenceSpecification, this is exactly one Lifeline (the one on which the event occurs). For CombinedFragment, it may be multiple Lifelines (all those spanned by the fragment box). Maps to UML 2.5.1 §17.3 InteractionFragment::covered [0..*] and §17.4 OccurrenceSpecification::covered [1] (redefines to exactly one). Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionFragment-covered", "OccurrenceSpecification-covered").

Depends Onop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#dependsOn

A relationship where a change to the supplier may affect the client. Maps to UML 2.5.1 §7.7 Dependency.

Deployed Onop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#deployedOn

A relationship from a DeployedArtifact to a DeploymentTarget. Maps to UML 2.5.1 §19.2 Deployment.

Executionop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#execution

The ExecutionSpecification that this ExecutionOccurrenceSpecification starts or finishes. This links the occurrence (a point in time) to the execution period it delimits. Maps to UML 2.5.1 §17.5 ExecutionOccurrenceSpecification::execution [1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="ExecutionOccurrenceSpecification-execution").

Execution Finishop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#executionFinish

The OccurrenceSpecification that marks the end of this ExecutionSpecification (the bottom of the activation bar). Typically this is the sendEvent of the reply message. Maps to UML 2.5.1 §17.5 ExecutionSpecification::finish [1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="ExecutionSpecification-finish").

Execution Startop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#executionStart

The OccurrenceSpecification that marks the beginning of this ExecutionSpecification (the top of the activation bar). Typically this is the receiveEvent of an incoming message. Maps to UML 2.5.1 §17.5 ExecutionSpecification::start [1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="ExecutionSpecification-start").

Extendsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#extends

A relationship from an extending UseCase to an extended UseCase. Maps to UML 2.5.1 §18.2 Extend.

Formal Gateop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#formalGate

The Gates that form the message interface between this Interaction and any InteractionUses which reference it. Formal gates define the "ports" through which messages can enter or leave a reusable Interaction. Maps to UML 2.5.1 §17.2 Interaction::formalGate [0..*] {composite}. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Interaction-formalGate").

Generalizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#generalizes

A taxonomic relationship between a more general Classifier and a more specific Classifier. Maps to UML 2.5.1 §9.7 Generalization. ODM Annex D.3.3 maps UML Generalization to rdfs:subClassOf. The direct triple uses this predicate; the qualified form carries metadata.

Guard Constraintop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#guardConstraint

The InteractionConstraint that guards an InteractionOperand. In UML, InteractionOperand::guard points to an InteractionConstraint instance (not directly to a string). This property provides the strict UML form; the :guard datatype property provides a pragmatic shortcut for simple cases. Maps to UML 2.5.1 §17.6 InteractionOperand::guard [0..1] {composite}. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionOperand-guard").
editorial note
Both :guard (string shortcut) and :guardConstraint (object form) are supported. Use :guard for simple textual guards in architecture models. Use :guardConstraint when you need to attach minint/maxint (for loops) or when round-tripping from XMI where the guard is a full InteractionConstraint.

Has Fragmentop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#hasFragment

The ordered set of InteractionFragments owned by this Interaction or InteractionOperand. Maps to UML 2.5.1 §17.2 Interaction::fragment [0..*] {ordered, composite} and §17.6 InteractionOperand::fragment [0..*] {ordered, composite}. The ordering of fragments defines the top-to-bottom temporal sequence in a sequence diagram. In RDF, the ordering is captured by :sequenceNumber on each fragment instance rather than by collection position. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Interaction-fragment", "InteractionOperand-fragment").
editorial note
In UML XMI, the fragment property is {ordered} — the XML document order of <fragment> elements defines temporal ordering. In RDF there is no inherent document order, so each fragment carries a :sequenceNumber integer. See UML-DD-9 in design-decisions.md for the rationale.

Has General Orderingop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#hasGeneralOrdering

The GeneralOrdering constraints owned by this InteractionFragment. Maps to UML 2.5.1 §17.3 InteractionFragment::generalOrdering [0..*] {composite}. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionFragment-generalOrdering").

Has Lifelineop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#hasLifeline

The Lifelines owned by this Interaction. Maps to UML 2.5.1 §17.2 Interaction::lifeline [0..*] {composite}. In the UML metamodel this is a composite association — the Interaction owns its Lifelines. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Interaction-lifeline").

Has Messageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#hasMessage

The Messages owned by this Interaction. Maps to UML 2.5.1 §17.2 Interaction::message [0..*] {composite}. The Interaction owns all Messages that define communications between its Lifelines. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Interaction-message").

Has Operandop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#hasOperand

The ordered set of InteractionOperands contained in this CombinedFragment. Each operand represents one branch (for alt), one iteration body (for loop), or one parallel track (for par). Maps to UML 2.5.1 §17.6 CombinedFragment::operand [1..*] {ordered, composite}. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="CombinedFragment-operand").

Imports Packageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#importsPackage

A relationship that allows the use of unqualified names to refer to members of the imported Package. Maps to UML 2.5.1 §12.2 PackageImport.

Includesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#includes

A relationship from a base UseCase to an included UseCase. Maps to UML 2.5.1 §18.2 Include.

Interaction Operatorop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#interactionOperator

The interaction operator that determines the semantics of this CombinedFragment. Values are from the InteractionOperatorKind enumeration in uml-reference-data.ttl: alt, opt, loop, break, par, seq, strict, critical, neg, assert, ignore, consider. Maps to UML 2.5.1 §17.6 CombinedFragment::interactionOperator. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="CombinedFragment-interactionOperator").

Merges Packageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#mergesPackage

A directed relationship between two Packages that indicates that the contents of the merged Package are combined into the receiving Package. Maps to UML 2.5.1 §12.2 PackageMerge.

Messageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#message

References the Message of which this MessageEnd is an endpoint. This is the inverse navigation from a MessageOccurrenceSpecification (or Gate) back to the Message it belongs to. In UML XMI, this appears as the "message" attribute on MessageOccurrenceSpecification elements. Maps to UML 2.5.1 §17.4 MessageEnd::message [0..1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="MessageEnd-message").
editorial note
This property is the inverse of sendEvent/receiveEvent. Both directions are provided for query convenience: from Message to its endpoints (sendEvent/receiveEvent) and from endpoint back to its Message (message). In strict UML, the authoritative direction is Message→MessageEnd; this inverse is a convenience property.

Message Kindop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#messageKind

The derived kind of the Message: complete, lost, found, or unknown. A Message is "complete" if both sendEvent and receiveEvent are present; "lost" if sendEvent is present but receiveEvent is absent; "found" if receiveEvent is present but sendEvent is absent; "unknown" if neither can be resolved. Maps to UML 2.5.1 §17.4 Message::messageKind {derived, readOnly}. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Message-messageKind").

Message Sortop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#messageSort

The sort of communication reflected by the Message. Values are from the MessageSort enumeration in uml-reference-data.ttl: synchCall (default), asynchCall, asynchSignal, createMessage, deleteMessage, reply. The messageSort determines the visual notation (solid vs. dashed arrow, filled vs. open arrowhead) and the behavioral semantics (blocking vs. non-blocking, creation vs. destruction). Maps to UML 2.5.1 §17.4 Message::messageSort. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Message-messageSort").
editorial note
Default value is synchCall. The signature must refer to an Operation (for synchCall, asynchCall, reply) or a Signal (for asynchSignal). See .reference/omg/uml/ptc-18-01-01.xmi constraint "signature_refer_to".

Ordering Afterop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#orderingAfter

The OccurrenceSpecification that must occur second in a GeneralOrdering constraint. This is the "after" end of the ordering relation. Maps to UML 2.5.1 §17.3 GeneralOrdering::after [1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="GeneralOrdering-after").

Ordering Beforeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#orderingBefore

The OccurrenceSpecification that must occur first in a GeneralOrdering constraint. This is the "before" end of the ordering relation. Maps to UML 2.5.1 §17.3 GeneralOrdering::before [1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="GeneralOrdering-before").

qualified abstractsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedAbstracts

has range
Abstraction c

qualified aggregatesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedAggregates

has range
Aggregation c

qualified associated withop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedAssociatedWith

has range
Association c

qualified composed ofop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedComposedOf

has range
Composition c

qualified depends onop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedDependsOn

has range
Dependency c

qualified deployed onop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedDeployedOn

has range
Deployment c

qualified extendsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedExtends

has range
Extend c

qualified generalizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedGeneralizes

has range
Generalization c

qualified imports packageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedImportsPackage

has range
Package Import c

qualified includesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedIncludes

has range
Include c

qualified merges packageop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedMergesPackage

has range
Package Merge c

qualified realizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedRealizes

has range
Realization c

qualified realizes interfaceop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedRealizesInterface

has range
Interface Realization c

qualified usesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#qualifiedUses

has range
Usage c

Realizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#realizes

A relationship between a specification (e.g., Interface) and its implementation (e.g., Class). Maps to UML 2.5.1 §7.7 Realization.

Realizes Interfaceop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#realizesInterface

A specialized Realization between a BehavioredClassifier and an Interface. Maps to UML 2.5.1 §10.4 InterfaceRealization.

Receive Eventop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#receiveEvent

References the MessageEnd (typically a MessageOccurrenceSpecification) that represents the receiving of this Message. The receiveEvent is the point on the target Lifeline where the message arrow terminates. If absent, the Message is "lost" (messageKind = lost). Maps to UML 2.5.1 §17.4 Message::receiveEvent [0..1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Message-receiveEvent").

Refers Toop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#refersTo

The Interaction that this InteractionUse references. The semantics is that the contents of the referred Interaction are copied into the enclosing Interaction at the position of the InteractionUse. Maps to UML 2.5.1 §17.7 InteractionUse::refersTo [1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="InteractionUse-refersTo").

Representsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#represents

References the ConnectableElement (Property, Port, or Parameter) within the classifier that contains the enclosing Interaction. This is what the Lifeline "stands for" — the participant whose behavior is being described. Maps to UML 2.5.1 §17.3 Lifeline::represents [0..1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Lifeline-represents").

Send Eventop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#sendEvent

References the MessageEnd (typically a MessageOccurrenceSpecification) that represents the sending of this Message. The sendEvent is the point on the source Lifeline where the message arrow originates. If absent, the Message is "found" (messageKind = found). Maps to UML 2.5.1 §17.4 Message::sendEvent [0..1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Message-sendEvent").

Signatureop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#signature

The signature of the Message — the specification of its content. It refers either to an Operation (for call/reply messages) or a Signal (for asynchronous signal messages). The name of the referenced element must match the name of the Message. Maps to UML 2.5.1 §17.4 Message::signature [0..1]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="Message-signature").

To Afterop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#toAfter

References the GeneralOrderings that specify OccurrenceSpecifications that must occur after this OccurrenceSpecification. This is the inverse navigation from an OccurrenceSpecification to the GeneralOrderings where it is the "before" element. Maps to UML 2.5.1 §17.4 OccurrenceSpecification::toAfter [0..*]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="OccurrenceSpecification-toAfter").

To Beforeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#toBefore

References the GeneralOrderings that specify OccurrenceSpecifications that must occur before this OccurrenceSpecification. This is the inverse navigation from an OccurrenceSpecification to the GeneralOrderings where it is the "after" element. Maps to UML 2.5.1 §17.4 OccurrenceSpecification::toBefore [0..*]. Source: .reference/omg/uml/ptc-18-01-01.xmi (xmi:id="OccurrenceSpecification-toBefore").

Usesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/uml/onto#uses

A Dependency where the client requires the supplier for its full implementation or operation. Maps to UML 2.5.1 §7.7 Usage.

Data Properties

Bodydp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#body

The textual body of a Comment or Constraint. Maps to UML 2.5.1 §7.2 Comment::body.
has range
string

Default Valuedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#defaultValue

The default value of a Property. Maps to UML 2.5.1 §9.5 Property::defaultValue.
has range
string

Effectdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#effect

An effect Behavior executed when a Transition fires. Maps to UML 2.5.1 §14.2 Transition::effect.
has range
string

File Namedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#fileName

The file name of an Artifact. Maps to UML 2.5.1 §19.3 Artifact::fileName.
has range
string

Guarddp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#guard

A guard condition expressed as a string. For InteractionOperands, this is the Boolean expression that determines whether the operand is executed. For Transitions (state machines), this is the condition that must be true for the transition to fire. Maps to UML 2.5.1 §17.6 InteractionOperand (via InteractionConstraint) and §14.2 Transition::guard.
has range
string

Is Abstractdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isAbstract

Whether the Classifier is abstract. Maps to UML 2.5.1 §9.2 Classifier::isAbstract.
has range
boolean

Is Behaviordp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isBehavior

Whether the Port provides the published functionality of the owning EncapsulatedClassifier. Maps to UML 2.5.1 §11.3 Port::isBehavior.
has range
boolean

Is Compositedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isComposite

Whether the State is a composite state containing Regions. Maps to UML 2.5.1 §14.2 State::isComposite.
has range
boolean

Is Conjugateddp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isConjugated

Whether the Port is conjugated (provided and required interfaces are swapped). Maps to UML 2.5.1 §11.3 Port::isConjugated.
has range
boolean

Is Deriveddp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isDerived

Whether the Property value is derived from other information. Maps to UML 2.5.1 §9.5 Property::isDerived.
has range
boolean

Is Indirectly Instantiateddp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isIndirectlyInstantiated

Whether the Component is instantiated indirectly. Maps to UML 2.5.1 §11.6 Component::isIndirectlyInstantiated.
has range
boolean

Is Leafdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isLeaf

Whether the RedefinableElement cannot be further redefined. Maps to UML 2.5.1 §7.6 RedefinableElement::isLeaf.
has range
boolean

Is Ordereddp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isOrdered

Whether the values of a multi-valued property are ordered. Maps to UML 2.5.1 §7.5 MultiplicityElement::isOrdered.
has range
boolean

Is Orthogonaldp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isOrthogonal

Whether the State has multiple Regions (orthogonal). Maps to UML 2.5.1 §14.2 State::isOrthogonal.
has range
boolean

Is Read Onlydp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isReadOnly

Whether the StructuralFeature is read-only. Maps to UML 2.5.1 §9.4 StructuralFeature::isReadOnly.
has range
boolean

Is Servicedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isService

Whether the Port is used to provide the published functionality of the owning Component. Maps to UML 2.5.1 §11.3 Port::isService.
has range
boolean

Is Staticdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isStatic

Whether the Feature is a classifier-level feature. Maps to UML 2.5.1 §9.4 Feature::isStatic.
has range
boolean

Is Uniquedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#isUnique

Whether the values of a multi-valued property must be unique. Maps to UML 2.5.1 §7.5 MultiplicityElement::isUnique.
has range
boolean

Lower Bounddp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#lower

The lower bound of the multiplicity interval. Maps to UML 2.5.1 §7.5 MultiplicityElement::lower.
has range
integer

Namedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#name

The name of a NamedElement. Maps to UML 2.5.1 §7.4 NamedElement::name.
has range
string

Sequence Numberdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#sequenceNumber

The ordinal position of an InteractionFragment within its enclosing Interaction or InteractionOperand. This property captures the temporal ordering that UML XMI encodes via document order of the {ordered} fragment collection. Fragment with sequenceNumber 1 occurs before fragment with sequenceNumber 2, and so on. This is the primary ordering mechanism for sequence diagrams in Linked.Archi RDF.
editorial note
Alternative approaches considered: 1. rdf:List — rejected because lists are awkward to query in SPARQL and don't support random access or insertion 2. rdf:Seq — deprecated in modern RDF usage 3. Blank node chains — rejected for the same SPARQL ergonomics reasons The integer index approach is simple, queryable (ORDER BY ?seq), and consistent with how BPMN SequenceFlow uses explicit ordering in Linked.Archi.
has range
integer

Upper Bounddp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#upper

The upper bound of the multiplicity interval. Use -1 for unlimited (*). Maps to UML 2.5.1 §7.5 MultiplicityElement::upper.
has range
integer

Visibilitydp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/uml/onto#visibility

The visibility of a NamedElement (public, private, protected, package). Maps to UML 2.5.1 §7.4 NamedElement::visibility. Values are modeled as SKOS concepts in uml-reference-data.ttl.
has range
string

Annotation Properties

createdap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/created

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/creator

definitionap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#definition

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/description

domain includesap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#domainIncludes

editorial noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#editorialNote

exampleap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#example

history noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#historyNote

licenseap back to ToC or Annotation Property ToC

IRI: http://creativecommons.org/ns#license

modifiedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/modified

pref labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#prefLabel

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/publisher

range includesap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#rangeIncludes

scope noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#scopeNote

sourceap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/source

statusap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/status

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/title

unqualified formap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#unqualifiedForm

was derived fromap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/prov#wasDerivedFrom

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.